Fix parse_xml type for tmpl #590
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
To add some context, this happens because |
|
I have the same issue after upgrading Ansible up to 8.5.0 |
KB-perByte
approved these changes
Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Change the parse_xml argument validation to require a type
strinstead of a typestringfortmpl.ISSUE TYPE
COMPONENT NAME
parse_xml
ADDITIONAL INFORMATION
Any simple call to parse_xml would render a flavour of the following error message:
fatal: [localhost]: FAILED! => {"msg": "[\"argument 'tmpl' is of type <class 'ansible.utils.native_jinja.NativeJinjaText'> and we were unable to convert to string: 'NoneType' object is not callable\"]"}